Method and apparatus for intranet searching

ABSTRACT

A method for processing an intranet includes crawling the intranet to identify at least some of the pages in the intranet, and determining, for each identified page, a number of links in a shortest path from a root page to the identified page.

FIELD OF THE INVENTION

The present invention relates to search engines for intranets.

BACKGROUND OF THE INVENTION

Search engines are often used to locate information of interest in anetwork, such as the entire Internet, or a more focused search of anenterprise intranet. In response to a user's query, a typical searchengine provides a rank-ordered list that includes brief descriptions ofthe uncovered content, as well as text links to the associated networkpages. The rank ordering of the list is typically based on a matchbetween words appearing in the query and words appearing in the content.Typical limitations in present search methodology often cause irrelevantcontent to be returned in response to a query. In particular, the wealthof available content can impair search engine efficacy since it isdifficult to separate irrelevant content from relevant content.

A typical engine selects pages, in part, based on the number ofappearances of keywords found in search pages. A page can be assigned arelevance corresponding to the number of incidences of a search term onthe page, normalized to the length of the page. Some engines seek toimprove search results by giving greater significance to Web pages thatare linked by a greater number of other pages, taking the number oflinks as an indicator of significance.

Most search engines follow the same basic procedure for processinginformation in a network-based collection of pages. The engine usescrawling and parsing techniques to form an index of terms found in thepages of the network. The index includes data that is used by the searchsystem to process queries and identify relevant pages. After the indexis built, queries may be submitted to the search engine. A queryrepresents the user's information request, and is expressed using aquery language and syntax defined by the search engine. The searchengine processes the query using the index data for the network, andreturns a hit-list of objects that the search engine identifies astopically relevant. The user may then select relevant objects from thehit-list for viewing and processing. A user of the engine may also use apage from the hit-list as a starting point for further navigationthrough the network.

SUMMARY OF THE INVENTION

A search tool, according to some principles of the invention, canorganize search results based on whether the results are associated withgeneric or specific subject matter content. For example, in response toa specific query, pages having related specific content can be returned,while, in response to a generic query, pages having related genericcontent can be returned. The search tool can involve any or all ofcrawling-related, parsing-related, and querying-related features.

Accordingly, in one aspect, the invention features a method forprocessing an intranet including pages, at least one of which is a rootpage. The processing methodology includes crawling the intranet toidentify at least some of the pages in the intranet, and determining,for each identified page, a number of links in a shortest path from aroot page to the identified page. A hierarchical level for theidentified page can be assigned in response to the determined number oflinks in the shortest path.

In another aspect, the invention features a method for parsing at leastone page of an intranet, where the page includes terms arranged in ahierarchical structure. The method includes parsing the page to identifyterms in the page, and determining, for identified terms, one or morespecificity-related parameters. The specificity-related parameters canbe associated with, for example, the location of the term in thehierarchical structure of the page, and/or with a tag-type associatedwith the term.

In still another aspect, the invention features a method for processinga query for an intranet. The method includes receiving a query thatincludes at least one search term, and determining a degree ofspecificity of the query.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a flow diagram of a method for crawling an intranet,in accordance with one embodiment of the present invention;

FIG. 2 illustrates a block diagram of a hierarchical organization of anintranet, which can be used to infer the specificity or generality ofeach page, according to principles of the present invention;

FIG. 3 illustrates a flow diagram of a method for parsing an intranet,in accordance with one embodiment of the present invention;

FIG. 4 illustrates a block diagram of a hierarchical organization of apage structure, which can be used to infer the specificity or generalityof each term in the page, according to principles of the presentinvention; and

FIG. 5 illustrates a flowchart of a method for processing a searchengine query, in accordance with one embodiment of the presentinvention.

DETAILED DESCRIPTION

Applicant has appreciated that conventional search engines often giveunsatisfactory results, due, for example, to the vast number of pagesavailable for search, and due to the often very broad search queriessubmitted by users. A broad query can lead to the return of many hitsthat are of little or no use to the searcher. Moreover, relevant hitsmay be buried deep in a list of search results, so that the searcher haslittle chance of finding a relevant page in the list.

Applicant has further appreciated that conventional search engines arenot well adapted to intranet searches. A user seeking generalinformation often enters generic search terms for a search query. Asearch engine may then return a lengthy hit list having pages ofinterest that a user may fail to notice because they are buried deep inthe list. Further, the list may include pages that have specific subjectmatter that is irrelevant to the general information sought.

The term “intranet” is used herein in a broad sense to refer a Web site(also known as a Web presence) or a private network (such as anemployees-only intranet, or a customers-only extranet.) Thus, someintranets are accessible by the public, while others have restrictedaccess. An intranet contains a collection of information linked togetherwith navigational tools such that the information is presented as beinga set of cohesive information.

An intranet includes pages, one or more of which are root pages at thetop of a hierarchical structure. A root page can be, for example, a homepage and/or a conceptual page. An intranet may be controlled by one ormore entities, but typically is controlled by, for example, a singlecompany, organization, or individual. An example of the structure of anintranet is illustrated in FIG. 2, which is discussed in more detailbelow.

Applicant have further appreciated that an intranet typically has ahierarchical structure in which pages are arranged at various levels,with each level being defined by the links needed to reach a page fromone or more root pages. The structure can be viewed as a branch-like orroot-like structure of a tree, with a root page at the base of the tree(i.e., at the top level of the tree roots, or the bottom level of thetree branches.) Pages at levels of greater distance from the root pagetypically have narrower and/or more detailed subject matter coveragethan pages at levels closer to the root page, which tend to have moregeneric content. In accordance with one embodiment of the invention, onecan influence the results obtained in response to a search queue,depending on whether the search queue seeks generic or specificinformation, as discussed further below.

A page refers to a file with formatting information that controls itsvisual layout when presented to a network user via a display as a page.A page has an associated network address. A page may also be referredto, for example as a node or a document. Typically, pages are linked toone or more other pages. A link may be followed by, for example,selecting a term associated with the link. Page content is oftenformatted through use of hypertext markup language (HTML). The followingdescription utilizes examples of HTML-based pages, but it should beunderstood that such examples are illustrative and non-limiting, andthat features of the invention are applicable to intranets that includepages based on any language, including languages other than HTML.

Individual pages can have a structural hierarchy. For example, anHTML-based page can have a node hierarchy associated with, for example,HTML tags including a root tag, and additional tags at various levelsrelative to the root tag. An example of this structure is shown in FIG.4, discussed below. Applicant has appreciated that information lower inthe hierarchy of a page is typically more specific, and higher in thepage is typically more general. In one embodiment, knowledge of thehierarchical location of information is used to influence resultsreturned in response to a generic or a specific search, as described inmore detail below.

The expression “conceptual page,” is used herein to refer to a page thatacts as a primary page or parent for a particular subject matter topic,such that the conceptual page for a topic is at the top of the hierarchyfor information specific to the topic. Links extending away from aconceptual page often provide additional information relating to thesubject matter topic of the conceptual page, i.e., such pages can act aschildren to a parent conceptual page.

The word “term” is used herein to refer to a word, phrase, symbol, orother unit of information present in a page. Users of an intranet maysearch for information of interest in an intranet by, for example,submitting to a search engine a query including one or more termsassociated with the information of interest.

The word “weight” is used herein to refer to a level of specificityrelated to a page or a term. It is also used to refer to a valueassigned to a page at the time of a query to determine the placement ofthe page in a result list returned to a searcher. For example, weightcan refer to the degree of specificity assigned to a page based on itshierarchy within an intranet, or to the degree of specificity of a termwithin a term hierarchy in a page.

Moreover, a page can be assigned specificity values associated with theterms in the page, and thus have different degrees of specificity foreach of the different terms located in the page. A page assigned agreater degree of specificity has a higher probability of specificsubject matter content than a page assigned a lesser degree ofspecificity, which has a relatively greater likelihood of generalsubject matter content.

A specificity can be assigned to a page/term combination, and determinedfrom, for example, the location of the page in an intranet structureand/or the location of a term within the page structure. When pageweights are assigned to pages in association with a degree of pagerelevance, for example, at the time of a query, pages of greaterpotential relevance can be directed toward, for example, the top of aquery response result list.

The invention, in various aspects, arises, in part, from the realizationthat an intranet search engine can exploit structural features common tointranets to provide search results of improved relevance and/or toreduce the time a user spends locating relevant information. Forexample, an intranet includes pages linked through a series of pagelevels at increasing distances from a home page, or a conceptual page.Applicant recognized that more distant pages in an intranet structuretend to include information of greater specificity. That is, Applicanthas recognized that intranet authors and designers tend to place moregeneral information in pages at or closer to a root page, and moredetailed, topically specific information further from the root page.

Moreover, corporate presence Web site managers, for example, tend toorganize a structure of their sites into groups of logical conceptareas. These concept areas can also be organized in a manner that placesmore specific content at a greater distance away from the concept's homepage than general content on the same subject. Thus, an intranet canhave link structures that tend to be organized into clusters of conceptsthat are themselves organized, via links, from general to specific.

Thus, near-level pages typically tend to cover broader subject matter ata more generic breadth, while more distant level pages typically tend toprovide more narrow, detailed, and specific information about someaspect of the subject matter of a base-, or near-base, level page. Thus,in one embodiment, according to principles of the invention, thestructure of an intranet can be exploited to provide more relevantsearch results by, for example, crawling pages in the intranet todetermine their hierarchical location, and inferring a degree ofspecificity of the crawled pages based on their hierarchical position.In another embodiment, a degree of specificity of content can beinferred based on structure within a page.

In one embodiment, described below, the information regarding pagehierarchy and hierarchy of terms within a page are used together. Theinvention, however, is not limited in this regard, as either feature canbe used either together or alone.

In another embodiment, once information regarding specificity isinferred, a search query can be examined to determine the level ofspecificity requested, then content having the described level ofspecificity can be returned.

According to principles of the invention, a search engine, for example,can exploit the above-described structural tendencies to provide morerelevant and/or more useful page hits. For example, pages having morespecific information can be pushed to the top of a hit list in responseto a relatively specific query, and pages having more generalinformation can be pushed to the top of a hit list in response to arelatively broad query. Thus, a user can, for example, more easily andquickly locate pages of interest by spending less time reviewing generalsubject matter pages when a specific query is made, or inappropriatespecific pages when a general query is made.

In contrast, conventional art search engines typically return pages, inresponse to a query, that include query terms; the pages may bereordered in response to, for example, the number of links directed to apage, which can be taken as an indicator of page importance.Conventional search engines, however, do not utilize features of thestructural hierarchy of an intranet, as described herein with respect tothe present invention. For example, a conventional search engine cantend to return high level pages having generic subject matter inresponse to a narrow query, or can return irrelevant deeper level pageshaving narrow subject matter in response to a broad query.

Thus, according to principles of the invention, a generic query can beused to direct a searcher to portions of an intranet that containgeneral subject matter related to the query; from these portions, userscan often find the information they need via further site navigationdown to pages having more specific and relevant subject matter.Conversely, a specific query can be used to direct a searcher toportions of an intranet that contain specific subject matter related tothe query.

FIG. 1 is a flow diagram of a method 100 for processing an intranet,according to one embodiment of the invention. The method 100 includes anact of crawling 110 the intranet to identify the pages in the intranet.Crawling 110 can be done in any suitable way, and thus is not limited toany particular techniques. Crawling 110 may identify all of the pages inthe intranet, but the invention is not limited in this respect, asprocessing of every page may not be needed.

The method also includes an act of determining 120, for each identifiedpage, a number of links in a shortest path from a root page to theidentified page. The shortest path can be determined in any suitableway. The path can be determined 120 as each page is identified 120.Alternatively, for example, pages can first be identified 110, and thenthe shortest path can be determined 120.

The method 100 also includes an act of storing 130 information for eachidentified page indicating the number of links in the shortest path fromthe at least one root page to the identified page, the informationspecifying a hierarchical level for the identified page in the intranet.The information can take any form. It can be the links, it can beinformation that rates specificity according to any scale, or any othersuitable way.

Thus, according to the embodiment of the invention of FIG. 1,information about the subject matter content of a page can be inferredfrom the intranet structure, such as the page hierarchy. For example, anidentified page having a shorter path to a root page has a likelihood ofbeing more general in its subject matter than an identified page havinga longer path from a root page, which can be assumed to hold relativelynarrower, more specific subject matter.

The shortest path is a path of first discovery of an identified pageupon crawling from a root page. The shortest path can be determined bybeginning a crawl from a root page, and proceeding to a next level ofpages via links embedded in the root page. Links embedded in the nextlevel of pages can similarly be followed deeper into the intranethierarchy. A link to a root page, embedded in a page deeper in thehierarchy, is preferably ignored because all pages in an intranet mayinclude such an embedded link, to enable a user to easily return to aroot page, such as a home page of the intranet. Thus, a shortest pathwill often be a function of links intentionally placed in pages of theintranet.

FIG. 2 is a diagram of an example of an intranet structure 200 that canbe processed by the method 100. The structure has a home page 201, firstlevel pages 210 (level 1 of FIG. 2) located one link from the home page,second level pages 220 (level 2 of FIG. 2) located two links from thehome page 201, and third level pages 230 (level 3 in FIG. 2) locatedthree links from the home page 210. According to principles of theinvention, first level pages 210 are inferred to contain subject matterthat is more general than subject matter contained in second level pages220. Similarly, second level pages 220 are inferred to contain subjectmatter that is more general than subject matter contained in third levelpages 230, and so on.

FIG. 3 illustrates is a flow diagram of a method 300 of parsing pages toglean additional information about content specificity based on thelocation and/or treatment of the terms within a hierarchy defined by aninternal structure of a page. The method 300 includes the acts ofparsing 310 at least one page to identify at least one term in the page,and determining 320, for each identified term, one or morespecificity-related parameters associated with a term specificity. Suchparameters include, for example, a page structure parameter and atag-type parameter. A page structure parameter can be, for example, adistance from a root of the page.

The method 300 can include an act of storing 330 information, for eachidentified term, indicating the specificity-related parameter, such asthe distance from the root. The information can thus specify ahierarchical level for the identified term in the page. Informationspecifying a hierarchical level for the identified term in the page cantake any form. It can be the levels from a root of a page, it can beinformation that rates specificity according to any scale, or any othersuitable way.

In accordance with one embodiment of the invention, term specificity canbe inferred, at lease in part, from the location of the term in aninternal page structure. For example, an HTML page has a node hierarchy,as illustrated with reference to FIG. 4. Although the followingdescription relates to HTML pages, embodiments of the invention can beapplied to intranet pages having other formats.

The HTML page hierarchy includes HTML tags, which in turn are typicallyassociated with inner text. In accordance with one embodiment, thesenode hierarchies can be used to infer general versus specific content ina page. For example, the closer the node containing the current innertext is to a page's root, the greater the likelihood that the inner textcontains general content that is not specifically focused on a specifictopic. Conversely, the further the node is located from the root, thegreater the likelihood that the inner text of the node is specific to aparticular topic.

Moreover, Applicant has appreciated that formatting aspects, such asbolding of a term, underlining of a term, and/or linking of a term, canindicate a greater level of significance of the term in association withgreater specificity, and also results in the text being located furtherfrom the root of the page.

The above-described page-level structural information can be used toinfer, for example, the weight that a page should have for a given termcontained in the document. Thus, for example, a page can be assigned agreater level of specificity for terms in the page identified asassociated with a greater level of specificity than other terms in thepage.

In one embodiment of the invention, term weights for a page arenormalized against the term weights for the same term in other pagesbased on page length. This normalization helps to prevent long pagesfrom appearing to be more specific than short pages; i.e., a page havinggreater length will tend to include more appearances of a term.Normalization, when used, can be performed in any suitable way.

FIG. 4 is a diagram of an example of an HTML-based page structure 400. Apage associated with the structure 400 could be located, for example, inan intranet having the structure 200 of FIG. 2, and could be processedby the method 300 described with reference to FIG. 3. The structure 400includes a root tag 401, a page heading tag 410, a page title tag 411,heading meta tags 412, a body tag 420 identifying the body portion ofthe page 400, a body heading tag 421, a body table tag 422, bodyparagraph tags 423 a, 423 b, bold font tags 424 a, 424 b, and anchortags 425 a, 425 b. Some of the tags have associated inner text 430 a,430 b, 430 c, which can be seen by a user when the page is displayed.These tag-types and their association with inner text are known in theHTML arts.

As discussed above, in some embodiments of the invention, terms in thepage structure 400 that are more distant from the root tag 401 can beidentified as corresponding to information of greater specificity. Forexample, the root tag 410 can be associated with level 0, the pageheading tag 410 and the body tag 420 can be associated with level 1, thepage title tag 411, heading meta tags 412, body heading tag 421, bodytable tag 422, and body paragraph tag 423 a can be associated with level2, and the body paragraph tag 423 b can be associated with level 3.

Moreover, a term that has additional formatting can be associated with agreater level of specificity. Additional formatting indicative ofspecificity can include, for example, a bold or other distinguishingfont or color, a hypertext link, and/or presence in a title or meta tag.Accordingly, terms can be associated with deeper levels of a pagehierarchical structure in correspondence to their additional formatting,if any.

Additional tag types can be indicative of a deeper level in a pagehierarchy. Such tag types include, but are not limited to, code tags.Term specificity can then be associated with term depth in the hierarchyof the page. Further, term specificity can be weighted according to tagtype, as described in more detail below. Thus, a specificity calculationcan be improved by utilizing an indication of specificity level providedby a tag type.

Preferably, inner text is assigned a level in the page hierarchy inassociation with its immediate node level. That is, a node can includeinner text, and children also having inner text. The inner text of thechildren is thus preferably viewed as residing at a different level ofthe hierarchy in comparison to the inner text immediately associatedwith the parent node.

As mentioned above, information regarding the specificity or generalityof content in a page can be inferred based both upon the position of thepage in an intranet hierarchy, as well as information controlling theposition of the content in the structure of a page. These two bases ofinformation regarding the specificity/generality of content can becombined in any suitable way, and an embodiment of the invention thatemploys both is not limited to any particular technique. Below, aspecific example is described that employs the two sources ofinformation, but this is merely an example, as determination of thespecificity/generality of content can be done in other ways.

Crawling 110 (see FIG. 2) to identify pages can be accomplished, forexample, by use of any suitable crawling technique, as described above,and is not limited to known techniques. For example, the intranet can becrawled via use of software robots, spiders, wanderers, worms, etc. toidentify pages. According to principles of the invention, informationabout the determined 120 number of links in a shortest path to anidentified page is retained. Crawling can commence, for example, from aroot page and/or from conceptual pages of the intranet, which can beidentified for the crawler in any suitable way.

Using techniques such as those described above, the acts of crawling 110and determining 120 can be used to gather link information to determinethe location of a page in an intranet structure. For example, crawling110 can provide a parameter, DL, identifying the page level for eachidentified page within the intranet. The parameter DL can be specifiedin any suitable way. For example, DL is conveniently identified as thedistance of a particular page from the root page in units of levels,where the root page is at level 0, and each successive level extendingaway from the root page is incremented by 1 relative to a previouslevel.

In this example, in addition to page levels determined during crawling110, nesting levels of terms within pages are determined for termsduring parsing of identified pages, as may be accomplished via use ofthe method 300. According to some principles of the invention, combininginformation regarding page position within an intranet hierarchy andcontent position within a page can be implemented through the use offormulae, examples of which are described next.

In this example, the following formulae relate to assigning termhierarchy within associated pages. A normalized term hierarchy for aterm in an identified page is defined as follows:NLW=NL−TTL,where NLW is a normalized term level, or specificity, associated with aterm in a particular page. NL is the raw term level of the term withinthe hierarchy of the particular page, as can be measured from a root tagof the page.

TTL is a threshold term level that defines a normalized minimum nestinglevel of the term for all pages of the intranet that include the term.The TTL has a constant value for a term for all pages identified thatinclude the term. For example, the TTL can be conveniently selected byfirst determining the maximum nesting level of a term in all pages thatinclude the term in an intranet. TTL can then be set at a level somedistance from the maximum term level. For example, if the maximumnesting level for a term is level 10, TTL for the term can be set tolevel 5. The NLW parameter will then eliminate pages having the term ata nesting level no deeper than level 5.

Alternatively, for example, TTL can be selected based on statisticalconsiderations. For example, TTL can be set at a level two standarddeviations above the maximum term level.

In whatever manner TTL is selected, the effect of the TTL parameter isto eliminate, for a term, pages that include the term only at highhierarchy levels with the page. The TTL parameter in effect chops noisefrom a list of pages including a term by eliminating pages that, thoughincluding the term, do not have a sufficient specificity to warrantpresentation to a searcher in a result list.

To further refine the specificity associated with a term, a termspecificity parameter, TW, for a term in a page, can be determined byadding the NLW parameter to a tag weight parameter, TagW, as follows:TW=TagW+NLW,where TW is a term specificity associated with an overall specificityassigned to a term, for a particular page, and TagW is a tag specificityparameter ascribed to the term based on a term's immediate parent's HTMLtag type. To accomplish this, tag types can be assigned constant valuesdefined across an intranet for each tag type. For example, a weight of 1can be assigned to the most common tag types across the intranet, whilegreater weights can be assigned to other tag types depending on theirrelative obscurity. For example, a tag having a weight of 2 can be halfas frequent as a tag having a weight of 1. Also, for example, tags in apage head can be treated differently than tags in the page body. Forexample, tags in the head can be given a tunable weight. That is, anysuitable procedure an be utilized to assign a specificity level to thevarious tag types.

For example, a tag can be assigned a value in part through statisticalanalysis, and in part through human selection. For example, tags canhave a value of 1 to 20, with greater values associated with greaterspecificity. A statistical analysis can, for example, yield thefrequency of tag use, with greater frequency indicating greatergenerality.

The above-described activities can be used to produce a term index ofpages in the intranet. The term index can include a listing of pagesthat contain a particular term, and a specificity value for the term foreach page, such as the TW parameter described above. Moreover, in someembodiments of the invention, an inverted keyword index, as known tothose having ordinary skill in the search arts, can be created forsearching at query time. An inverted keyword index can be searched toobtain a listing of pages that include search terms.

In some embodiments, an overall term specificity parameter (for example,the NTW parameter described below) is utilized, which is defined for apage relating to all appearances of a particular term in the page. Anormalized overall term specificity parameter, NTW, is defined asfollows:NTW=log (STW/ASTW).

STW is a sum of all the term specificity (TW) values for all appearancesof a term in a particular page. ASTW is an average of all STW parametervalues for a term for all pages in which the term appears across theentire intranet. The ratio of STW to ASTW provides a raw normalizedoverall term specificity, while NTW is a normalized overall termspecificity for a term in a page. NTW is expressed in terms of a log forconvenience; the base of the logarithm can be base 10 or another value.Use of the logarithm limits the range of NTW values, which is convenientfor calculational purposes.

The above-described example formulae can be used, for example, to assista response to a search engine query, as described with reference to FIG.5.

Referring next to FIG. 5, features of the invention can be exploited,for example, to improve the response of a search engine to a user query.FIG. 5 is a flow diagram of a method 500 for processing a search enginequery for an intranet, according to one embodiment of the invention. Themethod 500 includes receiving the query 510, where the query includes atleast one search term, and determining 520 a degree of specificity ofthe query.

The act of determining 520 can be done in any suitable way. In oneembodiment, the specificity is determined in an inverse relationship toa potential number of pages returned in response to the query. Thenumber of pages can be the number of pages that include any term foundin a query. For example, a query that explicitly requires any of severalsearch terms to appear in a returned page would provide such a potentialnumber of pages. Alternatively, the number of pages can be the number ofpages that include, for example, all of the search terms. Such apotential number of pages can be obtained if a query explicitly requiresall search terms to reside in a page, or if this requirement is adefault when no preference is provided.

The method 500 can include selecting 530 at least some pages of theintranet as matching the query. Selecting 530 can utilize a selectionprocess that depends, at least in part, on the degree of specificity ofthe query. The method 500 can also include ranking 540 at least someselected pages for presentation in response to the query. Ranking 540can utilize a ranking process that depends, at least in part, on thedegree of specificity of the query.

Ranking 540 can entail ranking pages according to a level of pagespecificity correlated with the level of specificity of the query. Thus,if a query is perceived as specific, a presented ranking can givepreference to pages having specific content. If a query is perceived asgeneric, or general, the ranking can give preference to pages havinggeneric, or general, subject matter content.

For example, pages can be ranked in a sorted order, in oneimplementation of the method 500, by assigning a relevance value, R, toeach selected page. For example, selected pages can be those that bestmatch all terms in a query. The R value assigned to each such page canthen determine a sort order of the selected pages for presentation to asearcher.

In one illustrative set of formulae for calculating page relevancevalues, R is defined as:R=log (r), whereNDL=IDL−TDL, andr=sum of ((twK*NTW)+(nlK*NDL)).The parameters in these formulae have the following definitions.

NDL is a normalized page level for each of the pages that will bereturned in response to a particular query. The NDL parameter provides aconnection between the search results and the specificity of selectedpages. The selected pages, as described below, can be further weightedaccording to the term parameters described above to further refine theresult list presented to a searcher.

IDL is a reverse page level, corresponding to the distance of aparticular page from a page at the maximum identified depth of all pagelevels across the intranet; each successive level away from the maximumdepth level is determined by decrementing by 1 from the prior pagelevel. Thus, IDL is similar to the page level parameter, DL, determinedduring parsing 110, as described above, with, however, the page levelmeasured from the level of the maximum depth of all identified pages ofthe intranet rather than from the root page.

TDL, a threshold page level, is a minimum page level at which subjectmatter content is assumed to be significant. The value of TDL isselected in response to the specificity of a particular query, whichitself is determined by a number of page hits in response to the query.The TDL can be determined empirically. For example, a range of TDLvalues can be assigned to a range of numbers of page hits. For example,if a maximum page level is 10, a particular specificity of a particularquery can be assigned a TDL value of 5. In this example, calculation ofNDL would serve to eliminate all pages in a hit list having page levelsof less than 5.

Thus, TDL can be dependent on the specificity of a query. Thus, forexample, a deeper TDL can be selected for a more specific query since apage level further from a root is likely to be more relevant for a morespecific query. When TDL is subtracted from the IDL parameter, pagesthat have a negative NDL parameter value are dropped. Thus, pages thatremain in a list of pages that include the query terms are those havinga specificity greater than a level selected by the action of the TDLparameter.

R is the relevance assigned to a page selected in response to a query. Rcontrols the sort order of a list of pages returned from a search inresponse to a particular query. R is calculated as a log of a rawrelevance value (see r, below) to limit the range of R values to residefrom 0 to 1. Limiting the range of values can be convenient forcomputational purposes. Moreover, the calculated values can be truncatedto use, for example, only four digits, to further limit thecomputational requirements imposed by a search.

r is the raw relevance of each page selected in response to a query, andis the sum of the normalized overall term specificity (NTW) parameter,adjusted by a term weight coefficient (twK, see below), and thenormalized page level (NDL), adjusted by a page weight coefficient (nlK,see below). Thus, the raw relevance provides a ranking of page hitscorrelated to both a page specificity parameter and a term-within-a-pagespecificity parameter.

twK is a term level coefficient, which is used, with the page levelcoefficient (see nlK,) to balance the effect given to the normalizedoverall term specificity (NTW) with the effect given to the normalizedpage level (NDL) in the calculation of the raw relevance, r. nlK is apage level coefficient. twK and nlK are selected to obtain a desiredbalance between the use of term specificity and page specificity in arelevance determination.

This balance can be chosen in any suitable manner. twK and nlk can beconstants for all queries, or can be adjusted for different queries. twKand nlk can selected, at least in part, to adjust the units of the valueof NTW, which is in term level values, and the units of the value ofNDL, which is in page level values.

These constants can be assigned values of, for example, 0, 1, 2, orhigher to vary the relative weights given to term specificity and pagelevel in a relevance calculation. The values can be selected in anysuitable manner. For example, a sample user group can be presented withsearch results generated with different assigned constant values, andthe user group can then identify which set of results is mostsatisfactory. Thus, for example, constant values can be selected via asubjective, empirical approach.

As described above, in one embodiment, the generality of the search termor terms of a query is a function of the number of pages in a potentialresult list. For example, a query including the word “windows” on theMicrosoft.com Web site will match hundreds of thousands of pages and, inaccordance with one embodiment of the invention, is treated as arelatively general search term for that site. Understanding that theterm “windows” is a generic query can enable a search engine, accordingto principles of the invention, to push up generic results in theresults set of pages, i.e., pages having broad subject matter will bepushed to the top of a results list presented to the user of the searchengine.

In contrast, a query having relatively few page hits can be deemedrelatively specific. In response, page hits at a greater distance from aroot page can be given a greater weight to push them towards the top ofa results list. General content pages associated with lesser specificityvalues, as may exist near the root page, similarly can be pushed awayfrom the top of a list. A searcher can then be directed to pages havinga greater specificity of relevance to a search, to thus increase thespeed and/or likelihood of a successful search.

For example, through the above-described processes, pages having alonger path can be given a greater weight in response to a specificquery, while pages having a shorter path can be given a greater weightin response to a general query. Thus, a general query can receive, forexample, a list of pages with general pages pushed toward the top of thelist, while a specific query can receive a list of pages with specificpages pushed toward the top of the list.

The user presenting the general query thus need not sort through manypages having narrow undesired information. This user can start withgeneral subject matter pages, which can be more likely to lead a user topages having the desired information. Similarly, the user presenting thespecific query can avoid examination of pages having information that istoo general to satisfy the specific search.

It should be appreciated that some features of the methods 100, 300outlined herein may be coded as software that is executable on one ormore processors that employ any one of a variety of operating systems orplatforms. Additionally, such software may be written using any of anumber of suitable programming languages and/or conventional programmingor scripting tools, and also may be compiled as executable machinelanguage code.

It should be understood that the term “program” is used herein in ageneric sense to refer to any type of computer code or set ofinstructions that can be employed to program a computer or otherprocessor to implement various aspects of the present invention asdiscussed above. Additionally, it should be appreciated that accordingto one aspect of this embodiment, one or more computer programs thatwhen executed perform methods of the present invention need not resideon a single computer or processor, but may be distributed in a modularfashion amongst a number of different computers or processors toimplement various aspects of the present invention.

Various aspects of the present invention may be used alone, incombination, or in a variety of arrangements not specifically discussedin the embodiments described in the foregoing and is therefore notlimited in its application to the details and arrangement of componentsset forth in the foregoing description or illustrated in the drawings.In particular, each of the top-level activities may include any of avariety of sub-activities. For example, the top-level activitiesdescribed herein may include one or any combination of sub-activitiesdescribed herein or may include other sub-activities that refine thehierarchical structure of instructing and administering a patchmanagement process.

Use of ordinal terms such as “first”, “second”, “third”, etc., in theclaims to modify a claim element does not by itself connote anypriority, precedence, or order of one claim element over another or thetemporal order in which acts of a method are performed, but are usedmerely as labels to distinguish one claim element having a certain namefrom another element having a same name (but for use of the ordinalterm) to distinguish the claim elements.

Also, the phraseology and terminology used herein is for the purpose ofdescription and should not be regarded as limiting. The use of“including,” “comprising,” or “having,” “containing”, “involving”, andvariations thereof herein, is meant to encompass the items listedthereafter and equivalents thereof as well as additional items.

1. A method for processing an intranet comprising a plurality of pagesincluding at least one root page, the method comprising acts of: (A)crawling the intranet to identify at least some of the plurality ofpages in the intranet; and (B) determining, for at least one identifiedpage, a number of links in a shortest path from the at least one rootpage to the identified page.
 2. The method of claim 1, furthercomprising an act of: (C) storing information for the at least oneidentified page indicating the number of links in the shortest path fromthe at least one root page to the identified page, the informationspecifying a hierarchical level for the identified page in the intranet.3. The method of claim 2, further comprising an act (D) of defining asubject matter specificity level for the identified page in correlationto the hierarchical level of the identified page.
 4. The method of claim3, wherein the subject matter specificity level has a greater valve foran identified page having a greater number of links in its shortest pathfrom the at least one root page relative to a value for an identifiedpage having a fewer number of links in its shortest path from the atleast one root page.
 5. The method of claim 1, further comprising an act(C) of selecting a plurality of conceptual pages to be a plurality ofroot pages.
 6. The method of claim 1, wherein the act (C) comprisescrawling the intranet by beginning a plurality of crawls through theintranet starting from each of the plurality of root pages.
 7. Themethod of claim 1, wherein the act (A) comprises an act of identifyingall of the plurality of pages in the intranet.
 8. The method of claim 1,wherein at least one of the plurality of pages comprises HTMLformatting.
 9. The method of claim 1, wherein the intranet is associatedwith a Web site.
 10. The method of claim 1, further comprising an act(C) of determining a reverse page level associated with the number oflinks in the shortest path for each identified page.
 11. The method ofclaim 10, further comprising an act (D) excluding pages of theidentified pages having a shortest path with a number of links less thana threshold number of links.
 12. The method of claim 1, furthercomprising an act (C) of parsing each page of the plurality of pages toidentify any terms in the page.
 13. The method of claim 12, furthercomprising an act (D) of determining, for each identified term, adistance from a root node of the page.
 14. The method of claim 13,further comprising an act (E) of storing information, for eachidentified term, indicating the distance from the root, the informationspecifying a hierarchical level for the identified term in the page. 15.The method of claim 1, further comprising an act of (C) determining aspecificity of a query, the specificity of the query having an inverserelationship to a potential number of pages returned in response to thequery.
 16. The method of claim 15, further comprising an act (D) ofreturning, in response to the query, pages of the identified pageshaving a level of specificity associated with the level of specificityof the query.
 17. The method of claim 16, wherein the act (D) compriseslisting the returned pages in an order correlated to the level ofspecificity of the returned pages.